Skip to contentSkip to conversation

SSBI driver

U-Boot hanumant 2 participants 3 messages Nov 17, 2011 1 message not in the archive

lore
Share & tools
lore

hanumant

author
#0 lore raw

Hi

I am trying to implement a SSBI driver for a board. . The driver is
meant to be portable to multiple boards by the same vendor. Keeping this in mind

1)Would drivers/misc/ be the right location to implement this driver? 2)If not can I make a ($vendor)-common in the cpu directory to implement the driver given that the driver is going to be applicable for multiple socs by the same vendor. ie have something like the below. have arch/arm/cpu/armv7/($vendor)-common & arch/arm/cpu/armv7/($SOC). I believe there is already precedent for this?

Any input is appreciated.

Thanks
Hanumant

#1 lore raw

Dear hanumant,

Quoted 3 lines · In message <[email protected]> you wrote:

I am trying to implement a SSBI driver for a board. . The driver is
meant to be portable to multiple boards by the same vendor.

Maybe you would get more help if you explained what SSBI might be. Is it:

SSBI Single Scope Background Investigation
SSBI Species-Specific Biological Information
SSBI Salomon Smith Barney Inc. (bank)
SSBI Stichting Stimulering Bedrijfsmatig Imkeren

If you happen to mean "Single-Wire Serial Bus Interface" then you should probably use the more common name "1-wire".

Quoted 1 line

1)Would drivers/misc/ be the right location to implement this driver?

I would expect to find such drivers in drivers/w1/ as used in Linux.

Quoted 3 lines

2)If not can I make a ($vendor)-common in the cpu directory to implement the driver given that the driver is going to be applicable for multiple socs by the same vendor. ie have something like the below.

That makes no sense. If in doubt, look at the organization of the Linux tree. There such code is in drivers/w1/ and I see no reason why we would have to do different.

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de If you're not part of the solution, you're part of the problem.

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Dear hanumant,

please always keep the mailing list on Cc:

Quoted 4 lines · In message <[email protected]> you wrote:
Quoted 3 lines

If you happen to mean "Single-Wire Serial Bus Interface" then you should probably use the more common name "1-wire".

Thanks. Yes it is Single-Wire Serial Bus Interface.

...

Quoted 2 lines

Yes, now that you suggest this I do think this would be more appropriate. Though looking at the u-boot master branch, I don't find any drivers/w1.

We don't have generic 1-wire drivers yet. The only one I'm aware of is a custom driver deeply embedded into the code of ESD's CPCI405 board (see board/esd/cpci405/cpci405.c).

Quoted 2 lines

Do you suggest I create a w1 directory based on the linux kernel implementation and add my 1-wire (ssbi) driver to it.

Yes.

Best regards,

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If something is different, it's either better or worse,  and  usually
both.                                                    - Larry Wall